Aminet 4/Aminet 4 - November 1994.iso/aminet/dev/amos/amosl0794.lzh/AMOSLIST/[e-mail]_Mon Jul 25 21:53:09 1994.msg

Internet Message Format | 1994-08-01 | 4KB

Received: from hela.INS.CWRU.Edu by nfs1.digex.net with SMTP id AA20609
  (5.67b8/IDA-1.5 for <[e-mail]>); Mon, 25 Jul 1994 21:53:07 -0400
Received: from svcs1.digex.net (svcs1.digex.net [164.109.10.23]) by hela.INS.CWRU.Edu with SMTP (8.6.8.1+cwru/CWRU-2.1-freenet-gw)
    id VAA17766; Mon, 25 Jul 1994 21:52:52 -0400 (from [e-mail])
Received: by svcs1.digex.net id AA17626
  (5.67b8/IDA-1.5 for amos-out); Mon, 25 Jul 1994 19:27:30 -0400
Received: from nfs1.digex.net by svcs1.digex.net with SMTP id AA17622
  (5.67b8/IDA-1.5 for <[e-mail]>); Mon, 25 Jul 1994 19:27:28 -0400
Received: from post.demon.co.uk by nfs1.digex.net with SMTP id AA11850
  (5.67b8/IDA-1.5 for <[e-mail]>); Mon, 25 Jul 1994 19:27:22 -0400
Received: from dynamo.demon.co.uk by post.demon.co.uk id aa16608;
          26 Jul 94 0:08 GMT-60:00
Received: by dynamo.demon.co.uk (V1.16/Amiga)
    id AA0004x; Tue, 26 Jul 94 00:05:41 GMT
Date: Tue, 26 Jul 94 00:05:41 GMT
Message-Id: <[e-mail]>
Organization: Fortune Software
X-Mailviewer: Mail 1.12
From: Dominic Ramsey <[e-mail]>
To: [e-mail]
Subject: Re: Proposal
Status: RO

> >>   Given the likelihood (or is it certain now?) of the AMOS source code
> >> eventually going into the public domain, I think a team of programmers
> >> should be created which would work on improving AMOS, fixing the bugs,
> >> etc.  The team would discuss problems and send code through E-mail, and
> >> release updates occasionally.  This way work on AMOS could be
> >> coordinated and accomplished quickly, and there would be a single
> >> official version, rather than people going and making their own changes
> >
> >If you wanted it to be `official', you'd have to talk to Europress first.
> >If they release it as PD, then ANYONE will be able to do whatever they
> >want with it.
>
>   By "official", I mean "the version produced by a team of experienced
> programmers which everyone should use to maintain compatibility".
                             ^^^^^^

`Should' being the operative word. There is nothing to stop ANYONE else
setting up a similar group, releasing incompatible versions of AMOS.
This is where some kind of backing from Europress would be very useful,
even if it is just a mention in their doc files, when they release the
source code, with an address for the `Official AMOS Product Development
Team'.


> >>   If you would be interested in joining such a team, let me know.  You
> >> will need experience in assembler, since that's what AMOS is written in.
> >
> >I don't see any reason why assembler experience should be needed. There are
> >a lot of very experienced AMOS programmers who know nothing about assembler.
>
>   But knowing how to write AMOS code won't help fix AMOS itself!

But knowing how AMOS works *will* help. It is only people that have real
experience of AMOS that can tell you exactly what needs to be done to
improve it, and exactly what the bugs are. If the team is just a group
of assembler programmers, you will end up with a new version of
AMOS, that will only be of use to other assembler programmers, who will
not bother with it as they could do better in assembler!

AMOS was produced with the average user in mind, and should stay that way.
The only way you will do anything to improve it is to get maximum input
from the people who use it every day.

Also, lots of assembler programmers working on different aspects of one
program is bound to lead to problems. The Main Development Team for
AMOS Pro consisted of one main assembly programmer (Franois), and
eleven AMOS enthusiasts. Richard Vanner would ask us all what we wanted
to see in AMOS Pro, he would tell Franois, and Franois would go off
and do whatever he wanted! The system worked perfectly!
(Well, 97% perfectly according to Amiga Format and CU Amiga)

Perhaps you should ask Franois if he wants to be on the team! :)



---
Dominic Ramsey
[e-mail]